Methods, Systems, and Products for Address Translation

ABSTRACT

Methods, systems, and products translate addresses in residential networks. A residential gateway translates requests for content such that the residential gateway appears as both a requestor and a destination for requested content, regardless of an actual requesting device or a desired output device.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No.13/170,674 filed Jun. 28, 2011 and now issued as U.S. Pat. No. ______,and incorporated herein by reference in its entirety.

BACKGROUND

Exemplary embodiments generally relate to computers and networks and,more particularly, to content management in residential networks.

Homes today have many devices that receive content. A home networkcommonly has a desktop computer, a laptop computer, and even one or moretablet computers (such as an APPLE® IPAD®). Multiple smart phones (suchas Apple's IPHONE®) may also connect to the home network. Yet the homenetwork may also include a digital recorder, home theater, and evennetworked appliances (such as a networked refrigerator). The complexityof typical home networks has made content management cumbersome for mostusers.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

The features, aspects, and advantages of the exemplary embodiments arebetter understood when the following Detailed Description is read withreference to the accompanying drawings, wherein:

FIG. 1 is a simplified schematic illustrating an environment in whichexemplary embodiments may be implemented;

FIG. 2 is a more detailed schematic illustrating the operatingenvironment, according to exemplary embodiments;

FIGS. 3 and 4 are detailed schematics illustrating an addresstranslation, according to exemplary embodiments;

FIG. 5 is a detailed schematic illustrating another address translation,according to exemplary embodiments;

FIGS. 6-8 are flow diagrams illustrating distribution of content,according to exemplary embodiments;

FIG. 9 is a detailed schematic illustrating permissions and access,according to exemplary embodiments;

FIG. 10 is a schematic illustrating format conversions, according toexemplary embodiments;

FIG. 11 is a schematic illustrating standard content, according toexemplary embodiments;

FIG. 12 is a schematic illustrating a default destination, according toexemplary embodiments;

FIG. 13 is a schematic illustrating a graphical user interface,according to exemplary embodiments; and

FIGS. 14 and 15 are schematics depicting other possible operatingenvironments for additional aspects of the exemplary embodiments.

DETAILED DESCRIPTION

The exemplary embodiments will now be described more fully hereinafterwith reference to the accompanying drawings. The exemplary embodimentsmay, however, be embodied in many different forms and should not beconstrued as limited to the embodiments set forth herein. Theseembodiments are provided so that this disclosure will be thorough andcomplete and will fully convey the exemplary embodiments to those ofordinary skill in the art. Moreover, all statements herein recitingembodiments, as well as specific examples thereof, are intended toencompass both structural and functional equivalents thereof.Additionally, it is intended that such equivalents include bothcurrently known equivalents as well as equivalents developed in thefuture (i.e., any elements developed that perform the same function,regardless of structure).

Thus, for example, it will be appreciated by those of ordinary skill inthe art that the diagrams, schematics, illustrations, and the likerepresent conceptual views or processes illustrating the exemplaryembodiments. The functions of the various elements shown in the figuresmay be provided through the use of dedicated hardware as well ashardware capable of executing associated software. Those of ordinaryskill in the art further understand that the exemplary hardware,software, processes, methods, and/or operating systems described hereinare for illustrative purposes and, thus, are not intended to be limitedto any particular named manufacturer.

As used herein, the singular forms “a,” “an,” and “the” are intended toinclude the plural forms as well, unless expressly stated otherwise. Itwill be further understood that the terms “includes,” “comprises,”“including,” and/or “comprising,” when used in this specification,specify the presence of stated features, integers, steps, operations,elements, and/or components, but do not preclude the presence oraddition of one or more other features, integers, steps, operations,elements, components, and/or groups thereof. It will be understood thatwhen an element is referred to as being “connected” or “coupled” toanother element, it can be directly connected or coupled to the otherelement or intervening elements may be present. Furthermore, “connected”or “coupled” as used herein may include wirelessly connected or coupled.As used herein, the term “and/or” includes any and all combinations ofone or more of the associated listed items.

It will also be understood that, although the terms first, second, etc.may be used herein to describe various elements, these elements shouldnot be limited by these terms. These terms are only used to distinguishone element from another. For example, a first device could be termed asecond device, and, similarly, a second device could be termed a firstdevice without departing from the teachings of the disclosure.

FIG. 1 is a simplified schematic illustrating an environment in whichexemplary embodiments may be implemented. FIG. 1 illustrates aclient-server architecture for a residential network 20. A residentialgateway 22 communicates with the residential network 20 and with a datanetwork 24. The residential gateway 22 also communicates with one ormore networked devices 26 operating in the residential network 20.Today's home networks have many networked devices 26, such as desktopcomputers, laptop computers, cameras, digital recorders, a home theater,smart phones (e.g., an IPHONE®), and tablet computers (such as anIPAD®). Common appliances, like refrigerators, may also have networkcapability. The residential gateway 22 may thus interface with manynetworked devices 26 connected to, or communicating with, theresidential network 20.

The residential gateway 22 manages media content. When a user wants todownload content, the residential gateway 22 receives a request 30 forcontent from a requesting device 32 in the residential network 20. Therequest 30 for content describes some movie, music, or other content 34a user would like to experience. Here, though, the request 30 forcontent may also specify an output device 36 to which the content 34 isdestined. That is, even though the request 30 for content originatesfrom the requesting device 32, the user may specify the different outputdevice 36 to which the content 34 is eventually delivered. Theresidential gateway 22 thus brokers transactions between the requestingdevice 32, a content source 38, and the output device 36, such that thecontent 34 may be managed independent of devices (as later paragraphswill explain).

The residential gateway 22 thus recognizes preferred requesting devices.Today the user commonly has many networked devices 26, such as a desktopcomputer, a laptop computer, a digital recorder, a home theater, a smartphone (e.g., IPHONE®), and a tablet computer (such as an IPAD®). Commonappliances, like refrigerators, may also have network capability. Eventhough the user may have many networked devices 26, the user may preferto use a single device, or only a few devices, when surfing content. Theuser, for example, may prefer to surf the web using the IPHONE® orIPAD®. The user ordinarily does not surf from the digital recorder orthe refrigerator. Exemplary embodiments thus allow the user to makerequests from a preferred input device (such as the user's IPHONE® orIPAD®) and, yet, have the content 34 delivered to the different outputdevice 36. The residential gateway 22 thus allows the user to requestmovies, music, and other content without regard for the capabilities ofthe requesting device 32.

The residential gateway 22 may also receive the content 34 independentof the output device 36. Because the user may have many networkeddevices 26 in their residential network 20, not all of the networkeddevices 26 have the same capabilities. Some networked devices 26 may beunable to render certain video formats. Some networked devices 26 may beunable to render certain web content, and some networked devices 26 maybe unable to play certain file formats. Regardless, the residentialgateway 22 allows the user to request the content 34 without regard orconcern for the capabilities of the networked devices 26. The user mayselect any of the networked devices 26 as the output device 36. Theresidential gateway 22 brokers transactions such that the output device36 is transparent to the content source 38 (as later paragraphs willexplain). The residential gateway 22 may even format the content 34 tosuit the capabilities of the output device 36 (again, as laterparagraphs will explain).

Exemplary embodiments thus improve content sharing and distribution inthe residential network 20. Web-based gaming, IPTV programming, andother content may be requested, shared, and distributed without concernfor the requesting device 32 or for the output device 36. Theresidential gateway 22 provides a simple and convenient mechanism forordering the content 34, and the user's content experience is enhancedfor in-home media viewing. No increase in access bandwidth is needed inorder to support concurrent viewing. The user may use their preferredrequesting device 32 for convenient and faster access to the content 34.

FIG. 2 is a more detailed schematic illustrating the operatingenvironment, according to exemplary embodiments. The residential gateway22 has a processor 40 (e.g., “μP”), application specific integratedcircuit (ASIC), or other component that executes a gateway-side contentapplication 42 stored in a memory 44. The gateway-side contentapplication 42 includes an algorithm that identifies the residentialgateway 22 as both a requestor and as a destination of the requestedcontent 34. The gateway-side content application 42, however, mayoperate in any processor-controlled device, as later paragraphs willexplain.

The residential gateway 22 communicates with the requesting device 32 inthe residential network 20. The requesting device 32 also has aprocessor 50 (e.g., “μP”), application specific integrated circuit(ASIC), or other component that executes a client-side contentapplication 52 stored in a memory 54. The client-side contentapplication 52 may cooperate with the gateway-side content application42 to request and deliver the content 34 to the desired output device36. The client-side content application 52 includes an algorithm thatallows the user to graphically select the output device 36 as thedestination for the content 34. The client-side content application 52may cause the processor 50 to produce a graphical user interface (“GUI”)56. The graphical user interface 56 is illustrated as being visuallyproduced on a display device 58, yet the graphical user interface 56 mayalso have audible features. The client-side content application 52,however, may operate in any processor-controlled device, as laterparagraphs will explain.

The residential gateway 22 manages content requests. When the userwishes to request some movie, music, or other content, the user causesthe requesting device 32 to send the request 30 for content. The usersimply invokes various selection mechanisms from the graphical userinterface 56 (as later paragraphs explain). The request 30 for contentidentifies the content 34 that is desired. The user, though, may alsospecify which of the networked devices (illustrated as reference numeral26 in FIG. 1) shall receive the content 34. The user, in other words,specifies the output device 36 for the content 34 described in therequest 30 for content. The request 30 for content thus originates fromthe requesting device 32, but the user may specify the different outputdevice 36 to which the content 34 is eventually delivered. The request30 for content is sent along the residential network 20 to theresidential gateway 22.

The residential gateway 22 performs a first address translation 70. Whenthe residential gateway 22 receives the request 30 for content, thegateway-side content application 42 substitutes its gateway networkaddress 72 for the output device 36. That is, the gateway-side contentapplication 42 reformats the request 30 for content, such that therequest 30 for content appears to originate from the residential gateway22 itself. Even though the request 30 for content originated from therequesting device 32, the gateway-side content application 42 reformatsthe request 30 for content to identify its gateway network address 72 asan originator. Similarly, the gateway-side content application 42 mayalso reformat the request 30 for content to identify its gateway networkaddress 72 as a destination for the requested content. The request 30for content is thus translated to identify residential gateway 22 as therequestor and/or as the destination of the requested content 34. Thismechanism thus translates content requests to originate from theresidential gateway 22. Content requests are also translated to destineto the residential gateway 22.

The residential gateway 22 thus issues a translated request 74 forcontent. The translated request 74 for content identifies theresidential gateway 22 as the requestor and as the destination of thecontent 34. The gateway-side content application 42 causes the processor40 to send the translated request 74 for content into the data network24. The translated request 74 for content routes to some network addressassociated with the content source 38. The content source 38 retrievesthe requested content 34 and sends the content 34 back to theresidential gateway 22, as identified in the translated request 74 forcontent.

The residential gateway 22 then performs a second address translation80. When the residential gateway 22 receives the content 34, thegateway-side content application 42 then routes the content 34 to thedesired output device 36, as originally specified in the request 30 forcontent. The gateway-side content application 42 causes the processor 40to perform the second address translation 80 by substituting adestination network address 82 to the output device 36. The gateway-sidecontent application 42 reformats packets of data in the requestedcontent 34 to now identify the desired output device 36 as the finaldestination. The second address translation 80 may thus be one or morecustom-defined translation algorithms based on the user's preference forthe desired output device 36. The second address translation 80 may thusoverride the first address translation 70. The residential gateway 22thus routes the content 34 to the desired output device 36, asoriginally specified in the request 30 for content.

The residential gateway 22 thus manages the user's media content. Theresidential gateway 22 deliberately inserts itself to purposefullymanage media content. The residential gateway 22 brokers anytransactions to be independent of devices. The user may thus requestmovies, music, and other content without regard for the capabilities ofthe requesting device 32. Indeed, exemplary embodiments empoweruser-friendly, simple devices to request complicated,processor-intensive data. Easy-to-use preferred input devices may beused to designate more capable output devices. Exemplary embodimentseven allow the content 34 to be shared and distributed without concernfor the requesting device 32 or for the output device 36. Even thebandwidth capabilities of an Internet connection to the requestingdevice 32 are unimportant, as limited bandwidth is only needed to sendthe request 30 for content to the residential gateway 22. Mobile devicesare thus empowered to request bandwidth-intensive data.

FIGS. 3 and 4 are detailed schematics illustrating the first addresstranslation 70, according to exemplary embodiments. The requestingdevice 32 sends the request 30 for content to the gateway networkaddress 72 associated with the residential gateway 22. The request 30for content may include an identification of the requesting device 32.The requesting device 32, for example, may be identified by a devicetype (e.g., desktop computer, laptop computer, or phone), a network name(e.g., “Mary's IPAD®,” “kitchen computer,” or “Tom's phone”), and/or anoriginating network address (e.g., IP address or MAC address) associatedwith the requesting device 32. The request 30 for content may include anidentification of the output device 36. The output device 36, likewise,may be identified by the device type (e.g., USB drive, digital recorder,or set top box), the network name associated with the output device 36(e.g., “HDTV,” “DVR,” or “Home Computer”), and/or the destinationnetwork address 82 (e.g., IP address or MAC address) associated with thedesired output device 36. However the requesting device 32 and theoutput device 36 are identified, the request 30 for content routes tothe gateway network address 72 associated with the residential gateway22.

The gateway-side content application 42 then performs the first addresstranslation 70. As FIG. 3 illustrates, the gateway-side contentapplication 42 consults a residential network address translation table100. The residential network address translation table 100 isillustrated as being locally stored in the memory 54 of the residentialgateway 22, but the residential network address translation table 100may be remotely stored, queried, and accessed from any location in theresidential network 20 and/or in the data network 24 (illustrated,respectively, as reference numerals 20 and 24 in FIGS. 1 & 2).Regardless, the residential network address translation table 100 may bea user-defined translation that maps, relates, or otherwise associatesthe user's networked devices 26 to network addresses 102. Theresidential network address translation table 100 may be dynamicallypopulated as the networked devices 26 are discovered (perhaps using theknown Transmission Control Protocol/Internet Protocol (TCP/IP) networkprotocol). Entries in the residential network address translation table100 may be removed as any device is disconnected from the residentialnetwork 20. The gateway-side content application 42 may query theresidential network address translation table 100 to obtain the networkaddress 102 associated with the requesting device 32 and/or the outputdevice 36.

The gateway-side content application 42 generates the translated request30 for content. Even though the request 30 for content originated fromthe requesting device 32, the gateway-side content application 42translates, or spoofs, the request 30 for content to identify theresidential gateway 22 as both the requestor and the destination. Thegateway-side content application 42 generates the translated request 30for content to identify the gateway network address (“GNA”) 72 as anoriginating address 104 and as a destination address 106.

FIG. 4 illustrates a log 110 of content requests. The gateway-sidecontent application 42 may also log the translated request 30 forcontent. Because many requests for content may be received each day, thegateway-side content application 42 may maintain the log 110 of contentrequests. The log 110 of content requests is illustrated as beinglocally stored in the memory 54 of the residential gateway 22, but thelog 110 of content requests may be remotely stored, queried, andaccessed from any location in the residential network 20 and/or in thedata network 24. Regardless, the log 110 of content requests tracks therequesting device 32 and the desired output device 36 for each request30 for content. The gateway-side content application 42 may assign arequest identifier 112 to each request 30 for content. Each requestidentifier 112 may be any alphanumeric combination that uniquelyidentifies or differentiates the request 30 for content from otherrequests for content. FIG. 4 illustrates the log 110 of content as atable that maps, relates, or otherwise associates the request identifier112 of each request 30 for content to the requesting device 32, to thedesired output device 36, and to the requested content 34. The log 110of content thus allows the gateway-side content application 42 to trackwhat content 34 is requested for delivery. The log 110 of content mayalso assign a date and time stamp to the request 30 for content, thusfurther differentiating each request for content.

The translated request 30 for content is sent to the content source 38.The translated request 30 for content includes information thatidentifies the gateway network address 72 as the originating address 104and as the destination address 106. The translated request 30 forcontent includes the request identifier 112 that differentiates fromother requests for content. The translated request 30 for content routesto the source network address associated with the content source 38. Thecontent source 38 may be some computer, server, or other deviceaccessible from the data network 24. The content source 38 retrieves therequested content 34 and sends the content 34 back to the residentialgateway 22, as identified in the translated request 30 for content.

FIG. 5 is a detailed schematic illustrating the second addresstranslation 80, according to exemplary embodiments. When the residentialgateway 22 receives the content 34, one or more packets of data (e.g.,headers and/or payload) may also include the request identifier 112 thatdifferentiates from other requests for content. As the gateway-sidecontent application 42 receives the content 34, the gateway-side contentapplication 42 also receives the request identifier 112. Thegateway-side content application 42 again consults the log 110 ofcontent requests to determine the desired output device 36 associatedwith the request identifier 112 (as FIG. 4 illustrated). Thegateway-side content application 42 queries the log 110 of contentrequests for the request identifier 112 and retrieves the desired outputdevice 36.

The gateway-side content application 42 then consults the residentialnetwork address translation (“NAT”) table 100. Now that the originalrequesting device 32 and the desired output device 36 are known, thegateway-side content application 42 queries the residential networkaddress translation table 100 for the output device 36. Because theresidential network address translation table 100 maps the residentialnetwork addresses 102 to the networked devices 26, the gateway-sidecontent application 42 retrieves the residential network address 102associated with the desired output device 36. The residential networkaddress translation (“NAT”) table 100 may thus override a conventionalDNAT (Dynamic NAT), NAPT (Network Address Port Translation), and SNAT(Static Network Address translation) performed by conventional gateways.The residential network address translation table 100 may logicallyoverride, overlay, or ride above these conventional translations. Theresidential network address translation table 100 may be based oncustom-defined algorithms for translations that describe the user'spreference for the desired output device 36. The gateway-side contentapplication 42 causes the processor 40 to perform the second addresstranslation 80 by forwarding the requested content 34 to the residentialnetwork address 102 associated with the desired output device 36, asoriginally specified in the request 30 for content. The gateway-sidecontent application 42 thus uses the residential network address 102associated with the desired output device 36 as the destination networkaddress 82.

Exemplary embodiments thus permit content requests independent of inputdevices. The residential gateway 22 deliberately inserts itself intotransactional requests for media content. Movies, music, and otherbandwidth-intensive content may be requested without regard for thecapabilities of the requesting device 32. Simple, user-friendly inputdevices may request bandwidth-intensive, processor-intensive data.Exemplary embodiments thus empower mobile devices to requestbandwidth-intensive data without requiring a high-bandwidth connection.

FIGS. 6-8 are flow diagrams further illustrating distribution ofcontent, according to exemplary embodiments. FIG. 6 illustrates anexemplary flow where the requesting device 32 is also the desired outputdevice 36. The requesting device 32 sends the request 30 for content tothe residential gateway 22. The gateway-side content application 42performs the first address translation 70 and sends the translatedrequest 30 for content to the content source 38. The residential gateway22 receives the requested content 34 from the content source 38. Thegateway-side content application 42 performs the second addresstranslation 80 and sends the requested content 34 to the output device36.

FIGS. 7-8 illustrate shared distribution of the requested content 34,according to exemplary embodiments. The requesting device 32 sends therequest 30 for content to the residential gateway 22. Here, though, theuser has specified multiple output devices that receive or share therequested content 34. The gateway-side content application 42 performsthe first address translation 70, and the translated request 30 forcontent is sent to the content source 38. The residential gateway 22then receives the requested content 34. Here, though, because the userhas requested multiple output devices, the gateway-side contentapplication 42 performs the second address translation 80 to identifythe multiple desired output devices. The residential gateway 22 thussends the requested content 34 to the multiple output devices.

In FIGS. 6-8, the distribution of the inbound content 34 to the desiredoutput devices 36 may be controlled on an ad-hoc basis by using aTCP/UDP port field in the residential network address translation table100 of the residential gateway 22. The requested content 34 may also bemanaged using the multi-cast feature of the IP layer within residentialnetwork 20. The residential gateway 22 may manage all the IP-basednetworked devices 26 and manage broadcasting and multicasting sessionsand user authentications on each of devices in the within residentialnetwork 20. Each of the networked devices 26 (e.g., IP address or MACaddress) and their relationships with IP assignments in the residentialnetwork 20 may be accomplished via a multicast management solution basedon preference selections. Exemplary embodiments thus may not affecttransactions between the residential gateway 22 and the data network 24.All session, device, user, and authentication of the networked devices26 may be controlled in the residential gateway 22.

FIG. 9 is a detailed schematic illustrating permissions and access,according to exemplary embodiments. Here the user may be required tohave various credentials before selecting the desired output device 36.If the user wishes to send the requested content 34 to the output device36, the gateway-side content application 42 may require that the userhave permission 120 to direct the content 34 to the desired outputdevice 36. Likewise, the gateway-side content application 42 mayadditionally or alternatively require that the user have access 122 tothe desired output device 36. The gateway-side content application 42may manage all the IP networked devices 26 in the residential network 20to include the IP assignment, machine, and user IDs and theirrelationships to share permission based on the authentication andsession. For example, if User ID #1 on device #1 wants output on device#2, then User ID #1 needs permission and access on device #2. With thesession permission this information will be consumed by the gateway-sidecontent application 42 and will be applied when the residential gateway22 is distributing the content 34 in the residential network 20.

FIG. 10 is a schematic illustrating format conversions, according toexemplary embodiments. Because the capabilities of the requesting device32 are unimportant, the residential gateway 22 may format the requestedcontent 34 to suit the capabilities of the desired output device 36.That is, once the desired output device 36 is specified by the originalrequest 30 for content, the gateway-side content application 42 mayformat the requested content 34 to the display, processor, memory, andother capabilities of the desired output device 36. As FIG. 10illustrates, the gateway-side content application 42 may invoke aformatting module 130. The formatting module 130 accesses thecapabilities 132 associated with the desired output device 36. Theformatting module 130 may then access formatting rules 134 to convertthe content 34 to suit the capabilities of the desired output device 36.The requested content 34, for example, may be recolored, scaled, andeven reduced in resolution to suit the processing and displaycapabilities of the desired output device 36. Formatted content 136 isthen routed to the desired output device 36, as originally specified inthe request 30 for content.

FIG. 11 is a schematic illustrating standard content, according toexemplary embodiments. Because the capabilities of the requesting device32 are unimportant, exemplary embodiments make standardized content areality. That is, the requested content 34 may have a generic,standardized formatting 140 that is device neutral. FIG. 11, then,illustrates the residential gateway 22 receiving the requested content34 from the data network 24. Because the requested content 34 has thestandardized formatting 140, the gateway-side content application 42 mayadd formatting to the content 34. The gateway-side content application42 may invoke the formatting module 130 to format the content 34 to suitthe capabilities 132 of the desired output device 36. The formattingmodule 130 may retrieve and use the formatting rules 134 to convert thestandardized formatting 140 into a format more suited to the desiredoutput device 36. The formatted content 136 is then routed to thedesired output device 36, as originally specified in the request 30 forcontent.

FIG. 12 is a schematic illustrating a default destination 150, accordingto exemplary embodiments. Sometimes the user may wish to download thecontent 34, but no make a selection of the desired output device 36. Thegateway-side content application 42, in other words, permits anunspecified output device 152. If the request 30 for content does notspecify the output device 36, then the gateway-side content application42 may default to the gateway network address 72 associated with theresidential gateway 22. The content 34 will thus be delivered to theresidential gateway 22, as before, but the second address translation(illustrated as reference numeral 80 in FIGS. 2 & 5-8) need not beimmediately performed. The gateway-side content application 42, instead,may simply store the requested content 34 in the memory 44 of theresidential gateway 22 (or some other memory location). Later the usermay retrieve the requested content 34 and specify the desired outputdevice 36.

FIG. 13 is a schematic illustrating the graphical user interface 56,according to exemplary embodiments. As earlier paragraphs explained, thegraphical user interface 56 may be visually produced on the displaydevice (illustrated as reference numeral 58 in FIG. 2). The graphicaluser interface 56 allows the user to select the desired output device(s)36 for the requested content 34. As FIG. 13 illustrates, the graphicaluser interface 56 presents a listing 160 of the networked devices 26available to the residential network (illustrated as reference numeral20 in FIGS. 1 & 2). While any presentation is suitable, FIG. 13illustrates the listing 160 of the network devices 26 as a drop-downmenu 162. The user selects the desired output device(s) 36 from thedrop-down menu 162. The user, for example, maneuvers a cursor 164 andmakes a selection using a tactile input device, such as a mouse orkeyboard. The graphical user interface 56 may alternatively present anicon 166 for each networked device 26. The user selects the icon 166that corresponds to the desired output device 36.

Exemplary embodiments may be applied regardless of networkingenvironment. The residential network 20 may be a cable network operatingin the radio-frequency domain and/or the Internet Protocol (IP) domain.The residential network 20, however, may also include an intranet, alocal-area network (LAN), and/or a wide-area network (WAN). Theresidential network 20 may include coaxial cables, copper wires, fiberoptic lines, and/or hybrid-coaxial lines. The residential network 20 mayeven include wireless portions utilizing any portion of theelectromagnetic spectrum and any signaling standard (such as theI.E.E.E. 802 family of standards, GSM/CDMA/TDMA or any cellularstandard, and/or the ISM band). The residential network 20 may eveninclude powerline portions, in which signals are communicated viaelectrical wiring. The concepts described herein may be applied to anywireless/wireline communications network, regardless of physicalcomponentry, physical configuration, or communications standard(s).

The data network 24, likewise, may be applied regardless of networkingenvironment. The data network 24 may be a cable network operating in theradio-frequency domain and/or the Internet Protocol (IP) domain. Thedata network 24, however, may also include a distributed computingnetwork (such as the Internet), an intranet, a local-area network (LAN),and/or a wide-area network (WAN). The data network 24 may includecoaxial cables, copper wires, fiber optic lines, and/or hybrid-coaxiallines. The data network 24 may even include wireless portions utilizingany portion of the electromagnetic spectrum and any signaling standard(such as the I.E.E.E. 802 family of standards, GSM/CDMA/TDMA or anycellular standard, and/or the ISM band). The data network 24 may eveninclude powerline portions, in which signals are communicated viaelectrical wiring. The concepts described herein may be applied to anywireless/wireline communications network, regardless of physicalcomponentry, physical configuration, or communications standard(s).

FIG. 14 is a schematic illustrating still more exemplary embodiments.FIG. 14 is a generic block diagram illustrating the gateway-side contentapplication 42, and/or the client-side content application 52, operatingwithin a processor-controlled device 200. As paragraphs [0014] and[0015] explained, the gateway-side content application 42 and/or theclient-side content application 52 may operate in anyprocessor-controlled device 200. FIG. 14, then, illustrates thegateway-side content application 42, and/or the client-side contentapplication 52, stored in a memory subsystem of the processor-controlleddevice 200. One or more processors communicate with the memory subsystemand execute the gateway-side content application 42 and/or theclient-side content application 52. Because the processor-controlleddevice 200 is well-known to those of ordinary skill in the art, nodetailed explanation is needed.

FIG. 15 depicts other possible operating environments for additionalaspects of the exemplary embodiments. FIG. 15 illustrates thegateway-side content application 42, and/or the client-side contentapplication 52, operating within various other devices 300. FIG. 15, forexample, illustrates that the gateway-side content application 42 and/orthe client-side content application 52 may entirely or partially operatewithin a remote control 302, a set-top box (“STB”) 304, apersonal/digital video recorder (PVR/DVR) 306, a personal digitalassistant (PDA) 308, a Global Positioning System (GPS) device 310, aninteractive television 312, an Internet Protocol (IP) phone 314, a pager316, a cellular/satellite phone 318, or any computer system,communications device, or processor-controlled device utilizing theprocessor 40 and/or a digital signal processor (DP/DSP) 320. The device500 may also include watches, radios, vehicle electronics, clocks,printers, gateways, mobile/implantable medical devices, and otherapparatuses and systems. Because the architecture and operatingprinciples of the various devices 500 are well known, the hardware andsoftware componentry of the various devices 300 are not further shownand described.

Exemplary embodiments may be physically embodied on or in acomputer-readable storage medium. This computer-readable medium mayinclude CD-ROM, DVD, tape, cassette, floppy disk, memory card, andlarge-capacity disks. This computer-readable medium, or media, could bedistributed to end-subscribers, licensees, and assignees. A computerprogram product comprises a computer readable medium storingprocessor-executable instructions for managing content, as the aboveparagraphs explained.

While the exemplary embodiments have been described with respect tovarious features, aspects, and embodiments, those skilled and unskilledin the art will recognize the exemplary embodiments are not so limited.Other variations, modifications, and alternative embodiments may be madewithout departing from the spirit and scope of the exemplaryembodiments.

1. A method, comprising: receiving, at a processor, a request forcontent sent from a requesting address of a requesting device, therequest for the content specifying a different output device to whichthe content is delivered; storing, in memory, an association between therequest for the content, the requesting address, and a destinationaddress of the different output device; generating, by the processor, atranslated request that identifies a gateway network address as both arequestor and a destination for the content; and sending, by theprocessor, the translated request for the content.
 2. The method ofclaim 1, further comprising receiving the content.
 3. The method ofclaim 1, further comprising receiving the content addressed to thegateway network address.
 4. The method of claim 1, further comprisingretrieving the destination address associated with the different outputdevice.
 5. The method of claim 1, further comprising sending the contentto the destination address associated with the different output device.6. The method of claim 1, further comprising receiving a selection ofthe different output device in a graphical listing of output devices. 7.The method of claim 6, further comprising populating the graphicallisting with the output devices.
 8. A system, comprising: a processor;and a memory storing instructions that when executed causes theprocessor to perform operations, the operations comprising: receiving arequest for content sent from a requesting address of a requestingdevice, the request for the content specifying a different output deviceto which the content is delivered; storing an association between therequest for the content, the requesting address, and a destinationaddress of the different output device; generating a translated requestthat identifies a gateway network address as both a requestor and adestination for the content; and sending the translated request for thecontent.
 9. The system of claim 8, wherein the operations furthercomprise receiving the content.
 10. The system of claim 8, wherein theoperations further comprise receiving the content addressed to thegateway network address.
 11. The system of claim 8, wherein theoperations further comprise retrieving the destination addressassociated with the different output device.
 12. The system of claim 8,wherein the operations further comprise sending the content to thedestination address associated with the different output device.
 13. Thesystem of claim 8, wherein the operations further comprise receiving aselection of the different output device in a graphical listing ofoutput devices.
 14. The system of claim 8, wherein the operationsfurther comprise populating the graphical listing with the outputdevices.
 15. A memory storing instructions that when executed cause aprocessor to perform operations, the operations comprising: receiving arequest for content sent from a requesting address of a requestingdevice, the request for the content specifying a different output deviceto which the content is delivered; storing an association between therequest for the content, the requesting address, and a destinationaddress of the different output device; generating a translated requestthat identifies a gateway network address as both a requestor and adestination for the content; and sending the translated request for thecontent.
 16. The memory of claim 15, wherein the operations furthercomprise receiving the content.
 17. The memory of claim 15, wherein theoperations further comprise receiving the content addressed to thegateway network address.
 18. The memory of claim 15, wherein theoperations further comprise retrieving the destination addressassociated with the different output device.
 19. The memory of claim 15,wherein the operations further comprise sending the content to thedestination address associated with the different output device.
 20. Thememory of claim 15, wherein the operations further comprise receiving aselection of the different output device in a graphical listing ofoutput devices.